Track created issues in fix-test-failures agentic workflow#38823
Draft
Copilot wants to merge 6 commits into
Draft
Track created issues in fix-test-failures agentic workflow#38823Copilot wants to merge 6 commits into
fix-test-failures agentic workflow#38823Copilot wants to merge 6 commits into
Conversation
Co-authored-by: jeremymeng <7583839+jeremymeng@users.noreply.github.com>
Co-authored-by: jeremymeng <7583839+jeremymeng@users.noreply.github.com>
Copilot created this pull request from a session on behalf of
jeremymeng
June 4, 2026 16:53
View session
Co-authored-by: jeremymeng <7583839+jeremymeng@users.noreply.github.com>
Copilot
AI
changed the title
Updating workflow to include created issues in tracking
fix(workflows): update fix-test-failures tracking via add-comment safe-output and gh aw compile
Jun 4, 2026
Co-authored-by: jeremymeng <7583839+jeremymeng@users.noreply.github.com>
Copilot
AI
changed the title
fix(workflows): update fix-test-failures tracking via add-comment safe-output and gh aw compile
[EngSys] Reopen matching closed dependency-upgrade issues
Jun 4, 2026
Copilot stopped work on behalf of
jeremymeng due to an error
June 4, 2026 19:21
…undo eng/ changes Co-authored-by: jeremymeng <7583839+jeremymeng@users.noreply.github.com>
Copilot
AI
changed the title
[EngSys] Reopen matching closed dependency-upgrade issues
Reopen closed matching tracked issues in fix-test-failures workflow
Jun 4, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the fix-test-failures agentic workflow prompt/config so recurring failures that match previously tracked but now closed issues are detected and the corresponding issues are re-opened, preventing regressions from going unnoticed.
Changes:
- Adds
update-issueandadd-commentsafe-output tooling and documents logic to re-open matched closed issues. - Expands “Known Pre-existing Failures” matching to include tracking-issue comments, and adds a new Step 6 to record created issues back into the tracking issue.
- Regenerates
fix-test-failures.lock.ymlto reflect the new safe-outputs and tool list.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| .github/workflows/fix-test-failures.md | Adds safe-output tool configuration and prompt instructions to re-open closed tracked issues and to log created issues into the tracking issue comments. |
| .github/workflows/fix-test-failures.lock.yml | Regenerated compiled workflow reflecting new safe-outputs/tools and updated job permissions/outputs. |
Comment on lines
987
to
+991
| permissions: | ||
| contents: read | ||
| discussions: write | ||
| issues: write | ||
| pull-requests: write |
Comment on lines
1318
to
+1322
| permissions: | ||
| contents: read | ||
| discussions: write | ||
| issues: write | ||
| pull-requests: write |
jeremymeng
changed the title
fix-test-failures agentic workflow
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The fix-test-failures workflow checked issue #37864 for known pre-existing failures before filing new issues, but never wrote newly-created issues back to that tracking issue. This caused the known-failures list to always appear empty, resulting in duplicate issues on every run.
Changes
fix-test-failures.md
fix-test-failures.lock.yml — regenerated via gh aw compile fix-test-failures.md (not hand-edited)
Packages impacted by this PR
None (workflow/automation change only)
Describe the problem that is addressed by this PR
fix-test-failures workflow checked issue #37864 for known failures before creating new ones, but never recorded newly-created issues back into #37864. The tracking list stayed empty, causing duplicate issues on every scheduled run.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Option A (chosen): Use add-comment safe-output to post a structured tracking comment to Tracking: Known pre-existing CI test failures #37864 after each issue creation. Future runs read both the body and comments of Tracking: Known pre-existing CI test failures #37864. Fits naturally in the gh-aw safe-outputs framework, requires only .md changes + recompile, and issues: write is already granted to the safe_outputs job.
Option B: Custom safe-outputs: jobs: entry that updates the issue body. More complex, requires the custom job to depend on safe_outputs for the created issue URL — not straightforward in the gh-aw jobs dependency model.
Option C: Have the agent update Tracking: Known pre-existing CI test failures #37864 body directly via GitHub MCP. Not feasible in strict mode — agent only has issues: read.